Enter a type and click search.




Results for Magento\Payment\Model\Method\Adapter

File: vendor/amzn/amazon-pay-module/etc/di.xml

<virtualType name="AmazonFacade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Amazon\Payment\Gateway\Config\Config::CODE
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Magento\Payment\Block\Info
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            AmazonValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            AmazonValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            AmazonCommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual AmazonFacade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a AmazonFacade object that the following arguments should be used in the foo object's constructor.

  • $code = Amazon\Payment\Gateway\Config\Config::CODE;
  • $formBlockType = "Magento\Payment\Block\Form";
  • $infoBlockType = "Magento\Payment\Block\Info";
  • $valueHandlerPool = new AmazonValueHandlerPool (...)
  • $validatorPool = new AmazonValidatorPool (...)
  • $commandPool = new AmazonCommandPool (...)
Results for Magento\Payment\Model\Method\Adapter

File: vendor/klarna/module-kp/etc/di.xml

<virtualType name="KPVirtual"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Klarna\Kp\Model\Payment\Kp::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            KPValueHandlerPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            KPCommandPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            KPValidatorPool
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Klarna\Core\Block\Info\Klarna
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPVirtual object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a KPVirtual object that the following arguments should be used in the foo object's constructor.

  • $code = Klarna\Kp\Model\Payment\Kp::METHOD_CODE;
  • $valueHandlerPool = new KPValueHandlerPool (...)
  • $commandPool = new KPCommandPool (...)
  • $validatorPool = new KPValidatorPool (...)
  • $formBlockType = "Magento\Payment\Block\Form";
  • $infoBlockType = "Klarna\Core\Block\Info\Klarna";
Results for Magento\Payment\Model\Method\Adapter

File: vendor/magento/magento2-base/dev/tests/integration/_files/Magento/TestModuleFakePaymentMethod/etc/di.xml

<virtualType name="Magento\TestModuleFakePaymentMethod\Gateway\Facade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="string">
            fake
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form\Cc
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Magento\Payment\Block\ConfigurableInfo
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Config\ValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Validator\ValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Command\CommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual Magento\TestModuleFakePaymentMethod\Gateway\Facade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a Magento\TestModuleFakePaymentMethod\Gateway\Facade object that the following arguments should be used in the foo object's constructor.

Results for Magento\Payment\Model\Method\Adapter

File: vendor/magento/module-braintree/etc/di.xml

<virtualType name="BraintreeFacade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Magento\Braintree\Model\Ui\ConfigProvider::CODE
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Braintree\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Magento\Braintree\Block\Info
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeCommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeFacade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeFacade object that the following arguments should be used in the foo object's constructor.

Results for Magento\Payment\Model\Method\Adapter

File: vendor/magento/module-authorizenet-acceptjs/etc/di.xml

<virtualType name="AuthorizenetAcceptjsFacade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="string">
            authorizenet_acceptjs
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\AuthorizenetAcceptjs\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            AuthorizenetAcceptjsInfoBlock
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            AuthorizenetAcceptjsValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            AuthorizenetAcceptjsValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            AuthorizenetAcceptjsCommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual AuthorizenetAcceptjsFacade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a AuthorizenetAcceptjsFacade object that the following arguments should be used in the foo object's constructor.